USER-FRIENDLY WIRELESS SERVICE ACTIVATION PROCEDURE USING REMOTE eSIM PROVISIONING

ABSTRACT

Aspects of the subject disclosure may include, for example, identifying an assigned friendly-phrase embedded universal integrated circuit card identifier (fpEID) for a wireless communication device and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID. Various embodiments can include sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, and identifying the assigned fpEID based on the fpEID assignment confirmation message. Other embodiments are disclosed.

CROSS REFERENCE FOR RELATED APPLICATIONS

This application claims priority to and is a continuation of U.S. patent application Ser. No. 17/242,406 filed Apr. 28, 2021, which is a continuation of U.S. patent application Ser. No. 16/711,032 filed Dec. 11, 2019, now U.S. Pat. No. 11,039,305. The content of each of the foregoing are hereby incorporated by reference into this application as if set forth herein in full.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a user-friendly wireless service activation procedure using remote eSIM provisioning.

BACKGROUND

Traditionally, subscriber identity module (SIM) provisioning for wireless communication devices, such as cellular phones, has been a procedure that in most cases is completed prior to distribution of devices to their end users. However, for various reasons, it has become increasingly desirable over recent years to enable SIM provisioning to be performed after end users have taken possession of their devices. To this end, development has been ongoing of standards and procedures for remote SIM provisioning (RSP). Implementation of RSP allows wireless service providers to provision devices with embedded SIMs (eSIMs), without any need for physical access to those devices.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a block diagram illustrating an exemplary, non-limiting embodiment of a communications network in accordance with various aspects described herein.

FIG. 2 is a block diagram illustrating an example, non-limiting embodiment of an operating environment in accordance with various aspects described herein.

FIG. 3 depicts an illustrative embodiment of a first method in accordance with various aspects described herein.

FIG. 4 depicts an illustrative embodiment of a second method in accordance with various aspects described herein.

FIG. 5 depicts an illustrative embodiment of a third method in accordance with various aspects described herein.

FIG. 6 is a block diagram illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein.

FIG. 7 is a block diagram of an example, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

FIG. 8 is a block diagram of an example, non-limiting embodiment of a mobile network platform in accordance with various aspects described herein.

FIG. 9 is a block diagram of an example, non-limiting embodiment of a communication device in accordance with various aspects described herein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrative embodiments for enabling remote provisioning of an eSIM of a wireless communication device without requiring a user to enter an embedded universal integrated circuit card identifier (EID) of the wireless communication device. Some embodiments can include assigning a friendly-phrase EID (fpEID) to the wireless communication device. Various embodiments can include receiving, by a device vendor network, an EID retrieval request message sent by a service provider network, the EID retrieval request comprising the fpEID assigned to the wireless communication device. Some embodiments can include sending, by the device vendor network, an EID retrieval response message to the service provider network, the EID retrieval response message comprising an EID of the wireless communication device. Various embodiments can include authenticating the wireless communication device, by the device vendor network, prior to sending the EID retrieval response message to the service provider network. Other embodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include an apparatus, comprising a processing system for a wireless communication device, the processing system including a processor, and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations. The operations can comprise identifying an assigned friendly-phrase embedded universal integrated circuit card identifier (fpEID) for the wireless communication device and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID. Further operations can comprise sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, and identifying the assigned fpEID based on the fpEID assignment confirmation message.

One or more aspects of the subject disclosure include a non-transitory machine-readable medium, comprising executable instructions that, when executed by a processing system for a wireless communication device, the processing system including a processor, facilitate performance of operations. The operations can comprise identifying an fpEID for the wireless communication device and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID. Further operations can comprise sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, and identifying the assigned fpEID based on the fpEID assignment confirmation message.

One or more aspects of the subject disclosure include a method. The method can include identifying an fpEID for a wireless communication device and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID. The method can further include sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, and identifying the assigned fpEID based on the fpEID assignment confirmation message.

Referring now to FIG. 1 , a block diagram is shown illustrating an example, non-limiting embodiment of a communications network 100 in accordance with various aspects described herein. For example, communications network 100 can facilitate in whole or in part sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, identifying an assigned fpEID based on the fpEID assignment confirmation message, and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID. In particular, a communications network 125 is presented for providing broadband access 110 to a plurality of data terminals 114 via access terminal 112, wireless access 120 to a plurality of mobile devices 124 and vehicle 126 via base station or access point 122, voice access 130 to a plurality of telephony devices 134, via switching device 132 and/or media access 140 to a plurality of audio/video display devices 144 via media terminal 142. In addition, communication network 125 is coupled to one or more content sources 175 of audio, video, graphics, text and/or other media. While broadband access 110, wireless access 120, voice access 130 and media access 140 are shown separately, one or more of these forms of access can be combined to provide multiple access services to a single client device (e.g., mobile devices 124 can receive media content via media terminal 142, data terminal 114 can be provided voice access via switching device 132, and so on).

The communications network 125 includes a plurality of network elements (NE) 150, 152, 154, 156, etc. for facilitating the broadband access 110, wireless access 120, voice access 130, media access 140 and/or the distribution of content from content sources 175. The communications network 125 can include a circuit switched or packet switched network, a voice over Internet protocol (VoIP) network, Internet protocol (IP) network, a cable network, a passive or active optical network, a 4G, 5G, or higher generation wireless access network, WIMAX network, UltraWideband network, personal area network or other wireless access network, a broadcast satellite network and/or other communications network.

In various embodiments, the access terminal 112 can include a digital subscriber line access multiplexer (DSLAM), cable modem termination system (CMTS), optical line terminal (OLT) and/or other access terminal. The data terminals 114 can include personal computers, laptop computers, netbook computers, tablets or other computing devices along with digital subscriber line (DSL) modems, data over coax service interface specification (DOCSIS) modems or other cable modems, a wireless modem such as a 4G, 5G, or higher generation modem, an optical modem and/or other access devices.

In various embodiments, the base station or access point 122 can include a 4G, 5G, or higher generation base station, an access point that operates via an 802.11 standard such as 802.11n, 802.11ac or other wireless access terminal. The mobile devices 124 can include mobile phones, e-readers, tablets, phablets, wireless modems, and/or other mobile computing devices.

In various embodiments, the switching device 132 can include a private branch exchange or central office switch, a media services gateway, VoIP gateway or other gateway device and/or other switching device. The telephony devices 134 can include traditional telephones (with or without a terminal adapter), VoIP telephones and/or other telephony devices.

In various embodiments, the media terminal 142 can include a cable head-end or other TV head-end, a satellite receiver, gateway or other media terminal 142. The display devices 144 can include televisions with or without a set top box, personal computers and/or other display devices.

In various embodiments, the content sources 175 include broadcast television and radio sources, video on demand platforms and streaming video and audio services platforms, one or more content data networks, data servers, web servers and other content servers, and/or other sources of media.

In various embodiments, the communications network 125 can include wired, optical and/or wireless links and the network elements 150, 152, 154, 156, etc. can include service switching points, signal transfer points, service control points, network gateways, media distribution hubs, servers, firewalls, routers, edge devices, switches and other network nodes for routing and controlling communications traffic over wired, optical and wireless links as part of the Internet and other public networks as well as one or more private networks, for managing subscriber access, for billing and network management and for supporting other network functions.

FIG. 2 is a block diagram illustrating an example of an operating environment 200 in which the disclosed user-friendly procedure for wireless service activation using remote embedded subscriber identity module (eSIM) provisioning may be implemented according to various embodiments. In operating environment 200, a user 201 may wish to obtain wireless service for a wireless communication device (WCD) 202 featuring an eSIM 203. User 201 may select a wireless service provider, and a wireless service activation procedure may be initiated in order to obtain wireless service from the selected wireless service provider. Initiation of the wireless service activation procedure may be accomplished by opening/running, on wireless communication device 202, a service activation application for the selected wireless service provider. In conjunction with activating service for wireless communication device 202, the wireless service provider may remotely provision eSIM 203.

In order to remotely provision eSIM 203, the wireless service provider may require knowledge of an embedded universal integrated circuit card identifier (EID) 204 associated with eSIM 203. According to one approach, the service activation application may be configured to prompt user 201 to enter EID 204 during the service activation process. However, EID 204 may comprise a large sequence of numerals, such as a 32-digit number, and it may be difficult for user 201 to identify/find EID 204. Thus, requiring user entry of EID 204 may be burdensome upon user 201, and also prone to error.

According to the novel techniques disclosed herein, a user-friendly wireless service activation procedure may be implemented that absolves user 201 of the burden of manual EID entry. During service activation, rather than being required to type in EID 204, user 201 may merely need to provide a friendly-phrase EID (fpEID) 205. fpEID 205 may generally represent a phrase or text string that is shorter and/or easier to enter than EID 204.

In various embodiments, user 201 may request assignment of an fpEID for use in conjunction with service activation by providing user input 206. In some embodiments, user 201 may open a device vendor application on wireless communication device 202, and may provide user input 206 to the device vendor application in order to request fpEID assignment. In various embodiments, the device vendor application may be native to wireless communication device 202. In some other embodiments, the device vendor application may be downloaded onto wireless communication device 202 from an external source. In various embodiments, the device vendor application may represent particular functionality within the native device settings of wireless communication device 202. In some other embodiments, the device vendor application may represent a dedicated application that is separate from the native device settings of wireless communication device 202.

In various embodiments, based on received user input 206, wireless communication device 202 may detect the request for fpEID assignment. In response, in some embodiments, wireless communication device 202 may send an fpEID assignment request message 208 to an identity management framework 235 of a device vendor network 230. Device vendor network 230 may generally comprise a network of a device vendor associated with wireless communication device 202. Identity management framework 235 may generally comprise hardware and/or software that is operative to manage and track the assignment of fpEIDs to devices manufactured/sold by the device vendor, as well as the EIDs of those devices, and to handle requests for assignment of fpEIDs and retrieval of associated EIDs. In various embodiments, fpEID assignment request message 208 may comprise the EID 204 of wireless communication device 202.

In some embodiments, responsive to receipt of fpEID assignment request message 208, identity management framework 235 may assign fpEID 205 to wireless communication device 202. In various embodiments, the EID 204 of wireless communication device 202 and the assigned fpEID 205 of wireless communication device 202 may be stored by identity management framework 235. In some embodiments, an fpEID assignment confirmation message 210 may be sent from identity management framework 235 to wireless communication device 202 in order to notify wireless communication device 202 of the assignment of fpEID 205 to wireless communication device 202. In various embodiments, fpEID assignment confirmation message 210 may comprise the fpEID 205 that has been assigned to wireless communication device 202. In some embodiments, responsive to receipt of fpEID assignment confirmation message 210, fpEID 205 may be presented at wireless communication device 202 to inform user 201 of the assigned fpEID.

In various embodiments, the fpEID 205 that is assigned to wireless communication device 202 may be selected by identity management framework 235. In some other embodiments, wireless communication device 202 may present a user interface via which user 201 can specify a particular requested fpEID. In various embodiments, fpEID assignment request message 208 may include an indication of the requested fpEID that user 201 has specified, and identity management framework 235 may assign that requested fpEID to wireless communication device 202. The embodiments are not limited in this context.

In some embodiments, once it has been assigned fpEID 205, wireless communication device 202 may initiate a wireless service activation procedure in order to obtain service from a wireless service provider. In various embodiments, user 201 may use a service activation application associated with the wireless service provider to initiate the wireless service activation procedure. In some such embodiments, the service activation application may be a pre-installed application that is native to wireless communication device 202. In other embodiments, the service activation application associated with the wireless service provider may be downloaded onto wireless communication device 202 from an external source. The embodiments are not limited in this context.

In various embodiments, in order to initiate the wireless service activation procedure, wireless communication device 202 may send a service request message 212 to a service activation framework 245 of a service provider network 240. Service provider network 240 may generally comprise a network of the wireless service provider from which wireless service is to be obtained. Service activation framework 245 may generally comprise hardware and/or software that is operative to receive and fulfill requests for service activation received from wireless communication devices located within the wireless service area(s) of the wireless service provider. In some embodiments, service request message 212 may comprise the fpEID 205 that has previously been assigned to wireless communication device 202. In various embodiments, service request message 212 may additionally comprise device information 214. Device information 214 may generally comprise information that, alone or in combination with fpEID 205, uniquely identifies wireless communication device 202 to identity management framework 235. For example, according to some embodiments, device information 214 may comprise an international mobile equipment identity (IMEI) of wireless communication device 202. In various other embodiments, device information 214 may not be included in service request message 212. The embodiments are not limited in this context.

In some embodiments, in response to receipt of service request message 212, service activation framework 245 may send an EID retrieval request message 216 to identity management framework 235 in order to obtain the EID 204 for the eSIM 203 of wireless communication device 202. In various embodiments, EID retrieval request message 216 may comprise the fpEID 205 assigned to wireless communication device 202. In some embodiments, service request message 212 may include device information 214, and service activation framework 245 may include that device information 214 in EID retrieval request message 216. The embodiments are not limited in this context.

In various embodiments, based on the fpEID 205—and according to some implementations, device information 214—comprised in EID retrieval request message 216, identity management framework 235 may identify EID 204 as the EID to be provided to service activation framework 245 in response to EID retrieval request message 216. In some embodiments, identity management framework 235 may initiate an authentication procedure in order to confirm that the device attempting to activate service using EID 204 is authorized to do so. In various embodiments, the authentication procedure may implement multi-factor authentication.

In some embodiments, in conjunction with the authentication procedure, identity management framework 235 may send a device authentication query 218 to wireless communication device 202. In various embodiments, responsive to receipt of device authentication query 218, wireless communication device 202 may send authentication information 220 to identity management framework 235. In some embodiments, identity management framework 235 may then attempt to authenticate wireless communication device 202 based on authentication information 220. In various embodiments, upon a successful authentication of wireless communication device 202, identity management framework 235 may provide EID 204 to service activation framework 245. In some embodiments, identity management framework 235 may provide EID 204 by including it in an EID retrieval response message 222 that identity management framework 235 sends to service activation framework 245 in response to EID retrieval request message 216. The embodiments are not limited in this context.

FIG. 3 depicts an illustrative embodiment of a method 300 in accordance with various aspects described herein. While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 3 , it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

As shown in FIG. 3 , a user request for fpEID assignment may be detected at 302 based on received user input. For example, based on received user input 206 in operating environment 200 of FIG. 2 , wireless communication device 202 may detect a request on the part of user 201 for an fpEID assignment. At 304, an fpEID assignment request message comprising an EID of a wireless communication device may be sent to a device vendor network. For example, in operating environment 200 of FIG. 2 , wireless communication device 202 may send fpEID assignment request message 208 comprising EID 204 to identity management framework 235. At 306, an fpEID assignment confirmation message may be received that indicates an assigned fpEID for the wireless communication device. For example, in operating environment 200 of FIG. 2 , wireless communication device 202 may receive fpEID assignment confirmation message 210, which may indicate that fpEID 205 is an assigned fpEID for wireless communication device 202.

At 308, the assigned fpEID may be presented at the wireless communication device. For example, in operating environment 200 of FIG. 2 , wireless communication device 202 may present fpEID 205 on a display of wireless communication device 202. At 310, a service request message comprising the assigned fpEID may be sent to a service provider network to initiate a service activation procedure. For example, in operating environment 200 of FIG. 2 , wireless communication device 202 may send service request message 212 comprising fpEID 205 to service activation framework 245 in order to initiate a service activation procedure.

At 312, a device authentication query may be received from the device vendor network during the service activation procedure. For example, in operating environment 200 of FIG. 2 , wireless communication device 202 may receive device authentication query 218 from identity management framework 235 during a service activation procedure initiated at 310. At 314, device authentication information may be sent to the device vendor network in response to the received device authentication query. For example, in response to receipt of device authentication query 218 in operating environment 200 of FIG. 2 , wireless communication device 202 may send authentication information 220 to identity management framework 235. The embodiments are not limited to these examples.

FIG. 4 depicts an illustrative embodiment of a method 400 in accordance with various aspects described herein. While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 4 , it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

As shown in FIG. 4 , an fpEID assignment request message may be received at 402 that comprises an EID of a wireless communication device. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may receive fpEID assignment request message 208 comprising EID 204 from wireless communication device 202. At 404, an fpEID may be assigned to the wireless communication device. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may assign fpEID 205 to wireless communication device 202. At 406, the EID of the wireless communication device and the fpEID assigned to the wireless communication device 202 may be stored. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may store EID 204 and fpEID 205.

At 408, an fpEID assignment confirmation message may be sent that indicates the assigned fpEID. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may send fpEID assignment confirmation message 210, which may indicate fpEID 205. At 410, an EID retrieval request message comprising the assigned fpEID may be received from a service provider network. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may receive EID retrieval request message 216 from service activation framework 245, and EID retrieval request message 216 may comprise fpEID 205.

At 412, a device authentication query may be sent to the wireless communication device. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may send device authentication query 218 to wireless communication device 202. At 414, authentication information may be received from the wireless communication device in response to the device authentication query. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may receive authentication information 220 from wireless communication device 202 in response to device authentication query 218.

At 416, the wireless communication device may be authenticated based on the received authentication information. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may authenticate wireless communication device 202 based on authentication information 220. At 418, an EID retrieval response message comprising the EID of the wireless communication device may be sent to the service provider network. For example, in operating environment 200 of FIG. 2 , identity management framework 235 may send EID retrieval response message 222 to service activation framework 245, and EID retrieval response message 222 may comprise EID 204. The embodiments are not limited to these examples.

FIG. 5 depicts an illustrative embodiment of a method 500 in accordance with various aspects described herein. While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 5 , it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

As shown in FIG. 5 , a service request message may be received at 502 that comprises an assigned fpEID for a wireless communication device. For example, in operating environment 200 of FIG. 2 , service activation framework 245 may receive service request message 212 from wireless communication device 202, and service request message 212 may comprise fpEID 205.

At 504, an EID retrieval request message comprising the assigned fpEID may be sent to a device vendor network. For example, in operating environment 200 of FIG. 2 , service activation framework 245 may send EID retrieval request message 216 to identity management framework 235, and EID retrieval request message 216 may comprise fpEID 205.

At 506, an EID retrieval response message comprising an EID of the wireless communication device may be received from the device vendor network. For example, in operating environment 200 of FIG. 2 , service activation framework 245 may receive EID retrieval response message 222 from identity management framework 235, and EID retrieval response message 222 may comprise EID 204.

At 508, an eSIM of the wireless communication device may be remotely provisioned based on the EID. For example, based on the EID 204 comprised in the EID retrieval response message 222 received from identity management framework 235 in operating environment 200 of FIG. 2 , service activation framework 245 may provision eSIM 203. The embodiments are not limited to these examples.

Referring now to FIG. 6 , a block diagram 600 is shown illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein. In particular a virtualized communication network is presented that can be used to implement some or all of the subsystems and functions of communication network 100, the subsystems and functions of operating environment 200, and methods 300, 400, and 500 presented in FIGS. 1-5 . For example, virtualized communication network 600 can facilitate in whole or in part sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, identifying an assigned fpEID based on the fpEID assignment confirmation message, and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID.

In particular, a cloud networking architecture is shown that leverages cloud technologies and supports rapid innovation and scalability via a transport layer 650, a virtualized network function cloud 625 and/or one or more cloud computing environments 675. In various embodiments, this cloud networking architecture is an open architecture that leverages application programming interfaces (APIs); reduces complexity from services and operations; supports more nimble business models; and rapidly and seamlessly scales to meet evolving customer requirements including traffic growth, diversity of traffic types, and diversity of performance and reliability expectations.

In contrast to traditional network elements—which are typically integrated to perform a single function, the virtualized communication network employs virtual network elements (VNEs) 630, 632, 634, etc. that perform some or all of the functions of network elements 150, 152, 154, 156, etc. For example, the network architecture can provide a substrate of networking capability, often called Network Function Virtualization Infrastructure (NFVI) or simply infrastructure that is capable of being directed with software and Software Defined Networking (SDN) protocols to perform a broad variety of network functions and services. This infrastructure can include several types of substrates. The most typical type of substrate being servers that support Network Function Virtualization (NFV), followed by packet forwarding capabilities based on generic computing resources, with specialized network technologies brought to bear when general purpose processors or general purpose integrated circuit devices offered by merchants (referred to herein as merchant silicon) are not appropriate. In this case, communication services can be implemented as cloud-centric workloads.

As an example, a traditional network element 150 (shown in FIG. 1 ), such as an edge router can be implemented via a VNE 630 composed of NFV software modules, merchant silicon, and associated controllers. The software can be written so that increasing workload consumes incremental resources from a common resource pool, and moreover so that it's elastic: so the resources are only consumed when needed. In a similar fashion, other network elements such as other routers, switches, edge caches, and middle-boxes are instantiated from the common resource pool. Such sharing of infrastructure across a broad set of uses makes planning and growing infrastructure easier to manage.

In an embodiment, the transport layer 650 includes fiber, cable, wired and/or wireless transport elements, network elements and interfaces to provide broadband access 110, wireless access 120, voice access 130, media access 140 and/or access to content sources 175 for distribution of content to any or all of the access technologies. In particular, in some cases a network element needs to be positioned at a specific place, and this allows for less sharing of common infrastructure. Other times, the network elements have specific physical layer adapters that cannot be abstracted or virtualized, and might require special DSP code and analog front-ends (AFEs) that do not lend themselves to implementation as VNEs 630, 632 or 634. These network elements can be included in transport layer 650.

The virtualized network function cloud 625 interfaces with the transport layer 650 to provide the VNEs 630, 632, 634, etc. to provide specific NFVs. In particular, the virtualized network function cloud 625 leverages cloud operations, applications, and architectures to support networking workloads. The virtualized network elements 630, 632 and 634 can employ network function software that provides either a one-for-one mapping of traditional network element function or alternately some combination of network functions designed for cloud computing. For example, VNEs 630, 632 and 634 can include route reflectors, domain name system (DNS) servers, and dynamic host configuration protocol (DHCP) servers, system architecture evolution (SAE) and/or mobility management entity (MME) gateways, broadband network gateways, IP edge routers for IP-VPN, Ethernet and other services, load balancers, distributers and other network elements. Because these elements don't typically need to forward large amounts of traffic, their workload can be distributed across a number of servers—each of which adds a portion of the capability, and overall which creates an elastic function with higher availability than its former monolithic version. These virtual network elements 630, 632, 634, etc. can be instantiated and managed using an orchestration approach similar to those used in cloud compute services.

The cloud computing environments 675 can interface with the virtualized network function cloud 625 via APIs that expose functional capabilities of the VNEs 630, 632, 634, etc. to provide the flexible and expanded capabilities to the virtualized network function cloud 625. In particular, network workloads may have applications distributed across the virtualized network function cloud 625 and cloud computing environment 675 and in the commercial cloud, or might simply orchestrate workloads supported entirely in NFV infrastructure from these third party locations.

Turning now to FIG. 7 , there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. In order to provide additional context for various embodiments of the embodiments described herein, FIG. 7 and the following discussion are intended to provide a brief, general description of a suitable computing environment 700 in which the various embodiments of the subject disclosure can be implemented. In particular, computing environment 700 can be used in the implementation of network elements 150, 152, 154, 156, access terminal 112, base station or access point 122, switching device 132, media terminal 142, and/or VNEs 630, 632, 634, etc. Each of these devices can be implemented via computer-executable instructions that can run on one or more computers, and/or in combination with other program modules and/or as a combination of hardware and software. For example, computing environment 700 can facilitate in whole or in part sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, identifying an assigned fpEID based on the fpEID assignment confirmation message, and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID.

Generally, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

As used herein, a processing circuit includes one or more processors as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which can comprise computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 7 , the example environment can comprise a computer 702, the computer 702 comprising a processing unit 704, a system memory 706 and a system bus 708. The system bus 708 couples system components including, but not limited to, the system memory 706 to the processing unit 704. The processing unit 704 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 704.

The system bus 708 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 706 comprises ROM 710 and RAM 712. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 702, such as during startup. The RAM 712 can also comprise a high-speed RAM such as static RAM for caching data.

The computer 702 further comprises an internal hard disk drive (HDD) 714 (e.g., EIDE, SATA), which internal HDD 714 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 716, (e.g., to read from or write to a removable diskette 718) and an optical disk drive 720, (e.g., reading a CD-ROM disk 722 or, to read from or write to other high capacity optical media such as the DVD). The HDD 714, magnetic FDD 716 and optical disk drive 720 can be connected to the system bus 708 by a hard disk drive interface 724, a magnetic disk drive interface 726 and an optical drive interface 728, respectively. The hard disk drive interface 724 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 702, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 712, comprising an operating system 730, one or more application programs 732, other program modules 734 and program data 736. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 712. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer 702 through one or more wired/wireless input devices, e.g., a keyboard 738 and a pointing device, such as a mouse 740. Other input devices (not shown) can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 704 through an input device interface 742 that can be coupled to the system bus 708, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor 744 or other type of display device can be also connected to the system bus 708 via an interface, such as a video adapter 746. It will also be appreciated that in alternative embodiments, a monitor 744 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 702 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 744, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 702 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 748. The remote computer(s) 748 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 702, although, for purposes of brevity, only a remote memory/storage device 750 is illustrated. The logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 752 and/or larger networks, e.g., a wide area network (WAN) 754. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 702 can be connected to the LAN 752 through a wired and/or wireless communication network interface or adapter 756. The adapter 756 can facilitate wired or wireless communication to the LAN 752, which can also comprise a wireless AP disposed thereon for communicating with the adapter 756.

When used in a WAN networking environment, the computer 702 can comprise a modem 758 or can be connected to a communications server on the WAN 754 or has other means for establishing communications over the WAN 754, such as by way of the Internet. The modem 758, which can be internal or external and a wired or wireless device, can be connected to the system bus 708 via the input device interface 742. In a networked environment, program modules depicted relative to the computer 702 or portions thereof, can be stored in the remote memory/storage device 750. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer 702 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10BaseT wired Ethernet networks used in many offices.

Turning now to FIG. 8 , an embodiment 800 of a mobile network platform 810 is shown that is an example of network elements 150, 152, 154, 156, and/or VNEs 630, 632, 634, etc. For example, platform 810 can facilitate in whole or in part sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, identifying an assigned fpEID based on the fpEID assignment confirmation message, and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID. In one or more embodiments, the mobile network platform 810 can generate and receive signals transmitted and received by base stations or access points such as base station or access point 122. Generally, mobile network platform 810 can comprise components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, mobile network platform 810 can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform 810 comprises CS gateway node(s) 812 which can interface CS traffic received from legacy networks like telephony network(s) 840 (e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network 860. CS gateway node(s) 812 can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s) 812 can access mobility, or roaming, data generated through SS7 network 860; for instance, mobility data stored in a visited location register (VLR), which can reside in memory 830. Moreover, CS gateway node(s) 812 interfaces CS-based traffic and signaling and PS gateway node(s) 818. As an example, in a 3GPP UMTS network, CS gateway node(s) 812 can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s) 812, PS gateway node(s) 818, and serving node(s) 816, is provided and dictated by radio technology(ies) utilized by mobile network platform 810 for telecommunication over a radio access network 820 with other devices, such as a radiotelephone 875.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) 818 can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can comprise traffic, or content(s), exchanged with networks external to the mobile network platform 810, like wide area network(s) (WANs) 850, enterprise network(s) 870, and service network(s) 880, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform 810 through PS gateway node(s) 818. It is to be noted that WANs 850 and enterprise network(s) 870 can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s) or radio access network 820, PS gateway node(s) 818 can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s) 818 can comprise a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment 800, mobile network platform 810 also comprises serving node(s) 816 that, based upon available radio technology layer(s) within technology resource(s) in the radio access network 820, convey the various packetized flows of data streams received through PS gateway node(s) 818. It is to be noted that for technology resource(s) that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s) 818; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s) 816 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s) 814 in mobile network platform 810 can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can comprise add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by mobile network platform 810. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s) 818 for authorization/authentication and initiation of a data session, and to serving node(s) 816 for communication thereafter. In addition to application server, server(s) 814 can comprise utility server(s), a utility server can comprise a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through mobile network platform 810 to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) 812 and PS gateway node(s) 818 can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN 850 or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to mobile network platform 810 (e.g., deployed and operated by the same service provider), such as the distributed antennas networks shown in FIG. 1(s) that enhance wireless service coverage by providing more network coverage.

It is to be noted that server(s) 814 can comprise one or more processors configured to confer at least in part the functionality of mobile network platform 810. To that end, the one or more processor can execute code instructions stored in memory 830, for example. It is should be appreciated that server(s) 814 can comprise a content manager, which operates in substantially the same manner as described hereinbefore.

In example embodiment 800, memory 830 can store information related to operation of mobile network platform 810. Other operational information can comprise provisioning information of mobile devices served through mobile network platform 810, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory 830 can also store information from at least one of telephony network(s) 840, WAN 850, SS7 network 860, or enterprise network(s) 870. In an aspect, memory 830 can be, for example, accessed as part of a data store component or as a remotely connected memory store.

In order to provide a context for the various aspects of the disclosed subject matter, FIG. 8 , and the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the disclosed subject matter also can be implemented in combination with other program modules. Generally, program modules comprise routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

Turning now to FIG. 9 , an illustrative embodiment of a communication device 900 is shown. The communication device 900 can serve as an illustrative embodiment of devices such as data terminals 114, mobile devices 124, vehicle 126, display devices 144 or other client devices for communication via either communications network 125. For example, computing device 900 can facilitate in whole or in part sending an fpEID assignment request message to a device vendor network, receiving an fpEID assignment confirmation message from the device vendor network in response to the fpEID assignment request message, identifying an assigned fpEID based on the fpEID assignment confirmation message, and sending a service request message to a service provider network to initiate a service activation procedure, the service request message comprising the assigned fpEID.

The communication device 900 can comprise a wireline and/or wireless transceiver 902 (herein transceiver 902), a user interface (UI) 904, a power supply 914, a location receiver 916, a motion sensor 918, an orientation sensor 920, and a controller 906 for managing operations thereof. The transceiver 902 can support short-range or long-range wireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, or cellular communication technologies, just to mention a few (Bluetooth® and ZigBee® are trademarks registered by the Bluetooth® Special Interest Group and the ZigBee® Alliance, respectively). Cellular technologies can include, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise. The transceiver 902 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 904 can include a depressible or touch-sensitive keypad 908 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 900. The keypad 908 can be an integral part of a housing assembly of the communication device 900 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®. The keypad 908 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 904 can further include a display 910 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 900. In an embodiment where the display 910 is touch-sensitive, a portion or all of the keypad 908 can be presented by way of the display 910 with navigation features.

The display 910 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 900 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The display 910 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 910 can be an integral part of the housing assembly of the communication device 900 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.

The UI 904 can also include an audio system 912 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 912 can further include a microphone for receiving audible signals of an end user. The audio system 912 can also be used for voice recognition applications. The UI 904 can further include an image sensor 913 such as a charged coupled device (CCD) camera for capturing still or moving images.

The power supply 914 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 900 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.

The location receiver 916 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 900 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 918 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 900 in three-dimensional space. The orientation sensor 920 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 900 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).

The communication device 900 can use the transceiver 902 to also determine a proximity to a cellular, WiFi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 906 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 900.

Other components not shown in FIG. 9 can be used in one or more embodiments of the subject disclosure. For instance, the communication device 900 can include a slot for adding or removing an identity module such as a Subscriber Identity Module (SIM) card or Universal Integrated Circuit Card (UICC). SIM or UICC cards can be used for identifying subscriber services, executing programs, storing subscriber data, and so on.

The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and doesn't otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can comprise random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

In one or more embodiments, information regarding use of services can be generated including services being accessed, media consumption history, user preferences, and so forth. This information can be obtained by various methods including user input, detecting types of communications (e.g., video content vs. audio content), analysis of content streams, sampling, and so forth. The generating, obtaining and/or monitoring of this information can be responsive to an authorization provided by the user. In one or more embodiments, an analysis of data can be subject to authorization from user(s) associated with the data, such as an opt-in, an opt-out, acknowledgement requirements, notifications, selective authorization based on types of data, and so forth.

Some of the embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically identifying acquired cell sites that provide a maximum value/benefit after addition to an existing communication network) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence (class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to determine or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to predetermined criteria which of the acquired cell sites will benefit a maximum number of subscribers and/or which of the acquired cell sites will add minimum value to the existing communication network coverage, etc.

As used in some contexts in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.

Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Moreover, terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used herein, terms such as “data storage,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.

What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via one or more intervening items. Such items and intervening items include, but are not limited to, junctions, communication paths, components, circuit elements, circuits, functional blocks, and/or devices. As an example of indirect coupling, a signal conveyed from a first item to a second item may be modified by one or more intervening items by modifying the form, nature or format of information in a signal, while one or more elements of the information in the signal are nevertheless conveyed in a manner than can be recognized by the second item. In a further example of indirect coupling, an action in a first item can cause a reaction on the second item, as a result of actions and/or reactions in one or more intervening items.

Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement which achieves the same or similar purpose may be substituted for the embodiments described or shown by the subject disclosure. The subject disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure. For instance, one or more features from one or more embodiments can be combined with one or more features of one or more other embodiments. In one or more embodiments, features that are positively recited can also be negatively recited and excluded from the embodiment with or without replacement by another structural and/or functional feature. The steps or functions described with respect to the embodiments of the subject disclosure can be performed in any order. The steps or functions described with respect to the embodiments of the subject disclosure can be performed alone or in combination with other steps or functions of the subject disclosure, as well as from other embodiments or from other steps that have not been described in the subject disclosure. Further, more than or less than all of the features described with respect to an embodiment can also be utilized. 

What is claimed is:
 1. An apparatus, comprising: a processing system for a service activation framework of a service provider, the processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: receiving a wireless service request message to initiate a wireless service activation procedure, the wireless service request message being received from a wireless communication device and comprising an assigned friendly-phrase embedded universal integrated circuit card identifier (fpEID) for the wireless communication device, wherein the assigned fpEID for the wireless communication device is determined by the wireless communication device according to an fpEID assignment confirmation message obtained by the wireless communication device from an identity management framework of a device vendor; providing an EID retrieval request message to an identity management framework of a device vendor, the EID retrieval request message comprising the assigned fpEID for the wireless communication device; and receiving, from the identity management framework of the device vendor, an EID of the wireless communication device according to a successful authentication of the wireless communication device by the identity management framework.
 2. The apparatus of claim 1, wherein the EID retrieval request message includes device information associated with the wireless communication device.
 3. The apparatus of claim 1, wherein an fpEID assignment request message sent by the wireless communication device to the identity management framework comprises the EID of the wireless communication device.
 4. The apparatus of claim 3, wherein the fpEID assignment request message includes a requested fpEID, and wherein the assigned fpEID is equal to the requested fpEID.
 5. The apparatus of claim 1, wherein the EID retrieval request message further comprises an international mobile equipment identity (IMEI) of the wireless communication device.
 6. The apparatus of claim 1, wherein the EID of the wireless communication device and the assigned fpEID are stored by the identity management framework.
 7. A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processing system for a service activation framework of a service provider, the processing system including a processor, facilitate performance of operations, the operations comprising: receiving a wireless service request message to initiate a wireless service activation procedure, the wireless service request message being received from a wireless communication device and comprising an assigned friendly-phrase embedded universal integrated circuit card identifier (fpEID) for the wireless communication device, wherein the assigned fpEID for the wireless communication device is determined by the wireless communication device according to an fpEID assignment confirmation message obtained by the wireless communication device from an identity management framework of a device vendor; providing an EID retrieval request message to an identity management framework of a device vendor, the EID retrieval request message comprising the assigned fpEID for the wireless communication device, the EID retrieval request message including device information associated with the wireless communication device; and receiving, from the identity management framework of the device vendor, an EID of the wireless communication device.
 8. The non-transitory machine-readable medium of claim 7, wherein the receiving the EID of the wireless communication device is according to a successful authentication of the wireless communication device by the identity management framework.
 9. The non-transitory machine-readable medium of claim 7, wherein the EID retrieval request message includes device information associated with the wireless communication device.
 10. The non-transitory machine-readable medium of claim 7, wherein an fpEID assignment request message sent by the wireless communication device to the identity management framework comprises the EID of the wireless communication device.
 11. The non-transitory machine-readable medium of claim 10, wherein the fpEID assignment request message includes a requested fpEID, and wherein the assigned fpEID is equal to the requested fpEID.
 12. The non-transitory machine-readable medium of claim 7, wherein the EID retrieval request message further comprises an international mobile equipment identity (IMEI) of the wireless communication device.
 13. The non-transitory machine-readable medium of claim 7, wherein the EID of the wireless communication device and the assigned fpEID are stored by the identity management framework.
 14. A method, comprising: receiving, by a processing system for a service activation framework of a service provider, a wireless service request message to initiate a wireless service activation procedure, the wireless service request message being received from a wireless communication device and comprising an assigned friendly-phrase embedded universal integrated circuit card identifier (fpEID) for the wireless communication device, wherein the assigned fpEID for the wireless communication device is determined by the wireless communication device according to an fpEID assignment confirmation message obtained by the wireless communication device from an identity management framework of a device vendor; providing, by the processing system, an EID retrieval request message to an identity management framework of a device vendor, the EID retrieval request message comprising the assigned fpEID for the wireless communication device; and receiving, by the processing system from the identity management framework of the device vendor, an EID of the wireless communication device according to a successful authentication of the wireless communication device by the identity management framework.
 15. The method of claim 14, wherein the EID retrieval request message includes device information associated with the wireless communication device.
 16. The method of claim 14, wherein an fpEID assignment request message sent by the wireless communication device to the identity management framework comprises the EID of the wireless communication device.
 17. The method of claim 16, wherein the fpEID assignment request message includes a requested fpEID, and wherein the assigned fpEID is equal to the requested fpEID.
 18. The method of claim 14, wherein the EID retrieval request message further comprises an international mobile equipment identity (IMEI) of the wireless communication device.
 19. The method of claim 14, wherein the EID of the wireless communication device and the assigned fpEID are stored by the identity management framework.
 20. The method of claim 14, wherein the providing of the EID retrieval request message causes the identity management framework to send a device authentication query to the wireless communication device. 